| 1. | Innodb uses a finer grain of locking mechanism , row - level locking
Innodb使用更小粒度的锁定机制行级别的锁定。 |
| 2. | Row - level locking is automatic
行级锁定为自动。 |
| 3. | If table locking is not used , the default uses row - level locks , unless the
如果未使用表锁定，默认使用行级锁定，除非 |
| 4. | Row - level locks used
使用行级锁定 |
| 5. | By default , row - level locking is used for data pages , and page - level locking is used for index pages
默认情况下，行级锁定用于数据页，页级锁定用于索引页。 |
| 6. | After acquiring the stronger lock , all page - and row - level locks held by the transaction on the table are released
得到更强的锁后，事务在表上所持有的所有页级及行级锁都将予以释放。 |
| 7. | Specifies that a bulk update table - level lock is acquired for the duration of the bulk load operation ; otherwise , a row - level lock is acquired
指定在大容量加载操作期间获取大容量更新表级别的锁；否则，获取行级别的锁。 |
| 8. | Lock hints rowlock , updlock , and xlock that acquire row - level locks may place locks on index keys rather than the actual data rows
获取行级别锁的锁提示rowlock 、 updlock和xlock ，则可能对索引键而不是实际的数据行采用锁。 |
| 9. | There are little tricks one can do to increase concurrency , but if your applications need table - level or row - level locks , a dbms will better suit your needs
虽然有一些增加并发的技巧，但是，如果应用程序需要的是表级别或行级别的锁定，那么dbms能够更好地满足您的需求。 |
| 10. | Each index record contains a five - byte header that may be preceded by a variable - length header . the header is used to link together consecutive records , and also in row - level locking
每个索引记录包含一个五字节的头，在它之前还有一个变长的头。这个头是用来连接连续的记录，也用于行级锁。 |
